Multi-Community Instant Messaging System and Device

ABSTRACT

This relates to a mobile instant messaging device for communicating instant messages with different instant messaging communities. The device includes a display that displays community-specific icons, each icon specifying a different one of the instant messaging communities. A database stores characteristics of each of the communities. An instant messaging application is configured to communicate instant messages, with a member of the community of any of the icons selected by a user of the device, in conformity with the characteristics stored in the database for that community.

CROSS-REFERENCE TO RELATED APPLICATION

This is a continuation of U.S. patent application Ser. No. 10/730,682,filed on Dec. 8, 2003, hereby incorporated herein by reference.

BACKGROUND

1. Technical Field

This patent application relates generally to techniques for instantmessaging. More particularly, the technology described herein provides amulti-community instant messaging system and device in which a commoninstant messaging application operating on the device can be used tocommunicate with a plurality of instant messaging communities.

2. Description of the Related Art

Numerous instant messaging services are currently available, such as AIMand ICQ from America Online, Yahoo Messenger from Yahoo, and MSN fromMicrosoft. Each of these Instant Messaging services provide a communityof users with the ability to send and receive instant messages to oneanother. Using these instant messaging services on mobile devices hasbeen problematic. One solution is to provide a separate instantmessaging application for each of the services on the mobile device.This is problematic, however, because mobile devices typically havelimited fixed memory resources, and having four separate instantmessaging applications drains a great deal of the available devicememory. Another solution has been to provide a single, genericapplication and single user interface that connects to the variousInstant Messaging services through a separate gateway for each service.This solution is also problematic, however, because it sacrifices thefull range of functionality and unique interface attributes for any ofthe particular instant messaging services.

Instant messaging services exchange messages and state information (alsoreferred to as presence information) between users logged into theinstant messaging community. Each user typically receives stateinformation from only a subset of users that they are interested incommunicating with. In ICQ, for example, the presence information of aselect group of other ICQ clients is typically maintained in a “buddylist,” so that when the user of an ICQ client consults the list, theuser knows if any of the corresponding users in the “buddy list” areavailable for instant messaging, or if they are not. Presenceinformation in ICQ is defined using states such as connected, chatty,away, extended away, occupied, do not disturb, invisible, and offline.The other exemplary instant messaging applications mentioned above usedifferent terms to describe the buddy list and presence states, and mayalso provide a different set of functions and distant user interfaceattributes.

SUMMARY

A multi-community instant messaging system, device and method areprovided. The system includes a plurality of instant messagingcommunities, a network, and at least one mobile instant messagingdevice. The mobile instant messaging device provides a user interfacefor displaying a plurality community-specific icons, eachcommunity-specific icon providing an identification of one of theinstant message communities. The mobile device also provides a pluralityof configuration data files are stored on the device, each configurationdata file being associated with one of the community-specific icons, anda common instant messaging application. Upon selecting one of thecommunity-specific icons, the common instant messaging application isconfigured for use as a community-specific instant messaging applicationusing the associated configuration data file, and may communicateinstant messages over the network to the selected instant messagingcommunity.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram of a multi-community instant messaging systemand device;

FIG. 2 is a flow diagram showing triggering events forcommunity-specific icons in the device shown in FIG. 1; and

FIG. 3 is a block diagram of an exemplary mobile device for use with themulti-community instant messaging system shown in FIG. 1.

DETAILED DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram of a multi-community instant messaging system10 and device 12. The exemplary system 10 includes a plurality ofinstant messaging communities 14, 16, 18, 20, with corresponding usersof those communities, a wireless network 22 having one or more basestations 24, and one or more wireless mobile devices 12. Although thisexemplary system is shown as having a wireless interface between theinstant messaging communities 14, 16, 18, 20 and the mobile device 12,alternatively the system could be implemented entirely in a wiredenvironment.

The users of the various instant messaging communities are depicted bythe computers on the left-hand portion of the Figure. In practice, ofcourse, there would be a multitude of users for each community, andthese users could connect to the community through a variety ofnetworks, connections, etc., such as by wired connections through theInternet or a local or wide area network, through wirelesscommunications, such as cellular networks or satellite networks, overcable lines, or through direct TV satellite links, to name but a few.

Each of the instant messaging communities 14, 16, 18, 20 in thisexemplary system 10 are depicted as being connected to the wirelessnetwork 22. Although a direct link is shown in FIG. 1, there could beother intermediate systems and networks coupled between the wirelessnetwork 22 and the various instant messaging communities 14, 16, 18, 20.

The mobile device 12 is preferably a wireless mobile device, such as atwo-way pager, cellular telephone with data messaging capabilities,wireless Personal Digital Assistant, or the like, but could also be adevice that lacks a wireless interface. An exemplary wireless mobiledevice is depicted (and discussed below) with reference to FIG. 3.

The wireless mobile device 12 preferably includes a user interfaceribbon 26 for displaying program icons on a display of the device. Auser interface ribbon may be a one or two dimensional graphicaldepiction of a set of icons. The icons represent applications that maybe executed by a processor of the mobile device 12. For aone-dimensional ribbon there is a linear display of the available icons,which may be in a horizontal or vertical orientation on the display ofthe mobile device. For a two-dimensional ribbon there is a square orrectangular grid of icons. Furthermore, the icons displayed by the userinterface ribbon may be organized and displayed in a hierarchicalstructure such that certain root icons lead to other sets of icons, andso forth, in a hierarchical manner.

For each of the instant messaging communities 14, 16, 18, 20, there ispreferably a separate and distinct-looking icon displayed on the userinterface ribbon 26. For example, in the exemplary system of FIG. 1having four instant messaging communities 14, 16, 18, 20, there ispreferably four community-specific icons 28, 30, 32 and 34 that may bedisplayed on the user interface ribbon 26. Each of these icons ispreferably distinct from the others and provides information to the userof the device as to which community it represents. For example, the AIMicon 28 may include the letters “A”, “I”, and “M” in the graphicaldepiction so that a user of the mobile device knows that this iconrepresents the AIM instant messaging community. Alternatively, the iconsmy use graphic art that is associated with the particular instantmessaging community to convey to the user the identity of the communityaccessible via the particular icon. Although the mobile device 12 maydisplay a plurality of icons 28, 30, 32, 34 for instant messagingservices, each of these icons results in the configuration and executionof a common underlying application program 44, as discussed in moredetail below.

In addition to identifying a particular instant messaging service, thecommunity-specific icons 28, 30, 32, 34 may be configured to displayinstant messaging information to the user of the device. For example,the current presence (or state) information for the user may bedisplayed (either textually or graphically) along with the icon. Inaddition, current messaging information may be displayed (eithertextually or graphically) to indicate, for example, a number of receivedmessages or communications. Other types of information particular to thevarious instant messaging services may also be displayed along with theicon in order to provide the user with additional information that mayeffect the user's decision as to whether the instant messagingapplication 44 should be executed for the service identified by theicon.

When a user of the mobile device 10 selects one of the available instantmessaging icons 28, 30, 32, 34 on the user interface ribbon 26, thecommon, underlying instant messaging application program 44 is executedby the device's processor. Unlike the known single application systems,however, the instant messaging application 44 is configured for theparticular instant messaging community specified by the selected iconusing a community-specific configuration data file. This data file 36,38, 40, 42 includes information regarding the appearance, lexicon, andfunctionality of the particular community that is used to configure theinstant messaging application 44 for that particular community. Thus,for example, if certain terminology is used in AIM to describe thecontact list, or login procedure, or state information, etc., which isdistinct to this particular instant messaging service, then theconfiguration file 36 will provide this terminology to the instantmessaging application 44 so that the user experience is consistent withthe user of an AIM-specific instant messaging application. Similarly,the graphical appearance of the user interface for the AIM-specificapplication and its functionality are duplicated by the single,underlying IM application 44 using the data from the configuration datafile. For each of the other available instant messaging icons 30, 32,34, a similar configuration data file 38, 40, 42 will cause the sameunderlying instant messaging application 44 to be configured to operateand appear like a specific application for those instant messagingservices.

The database 46 stores information for each of the one or more instantmessaging services 14, 16, 18, 20 operable on the mobile device 12.Although depicted as a single database 46, this data may be stored inone or more databases. The data stored in this database may includepresence information for the user and also user-specific data for eachof the instant messaging services, such as buddy-lists, groups, storedcommunications, etc.

Although in one embodiment the various instant messaging icons 28, 30,32, 34 may be continuously displayed on the user interface ribbon 26, inthe example shown in FIG. 1 (and as further described with respect toFIG. 2), the display of a particular icon is triggered by the instantmessaging application 44. As discussed below, the instant messagingapplication may be configured to monitor one or more triggering eventsthat cause a particular instant messaging icon to be displayed and thensubsequently cause the configuration and execution of the single instantmessaging application 44 for that particular service. Although there ispreferably just one instant messaging application 44, it can be executedby the mobile device 12 more than once if the user has selected morethan one of the icons 28, 30, 32, 34, so that the user cansimultaneously communicate with the various instant messaging services14, 16, 18, 20.

FIG. 2 is a flow diagram showing triggering events forcommunity-specific icons in the device shown in FIG. 1. At step 52, theinstant messaging application monitors for a variety of possible triggersignals. These trigger signals may include: (1) receiving an invitationto chat (step 54); (2) receiving a service book record that identifies aparticular service accessible through one of the instant messagingservices (step 56); (3) entering of secret code by the user, or asreceived from another system or user (step 58); (4) activation of adownload file (step 60); (5) clicking on an HTML (or other type of) linkin a browser or other information service (step 62); or (6) receiving ane-mail (or other type of message) with a control code for activating aparticular service or session to another instant messaging user (step64). Other trigger signals may also be monitored. After detecting one ofthe trigger signals 54, 56, 58, 60, 62, etc., a particular one (or more)of the instant messaging services 14, 16, 18, 20 are configured usingthe appropriate configuration data file 36, 38, 40, 42, the instantmessaging application is executed at step 66 for that service, and thecommunity-specific icon for that instant messaging service is thendisplayed on the user interface ribbon at step 68.

FIG. 3 is a block diagram illustrating an example mobile communicationdevice 400 that may be used in conjunction with the user interfaceribbon 26, icons 28, 30, 32, 34, configuration data files 36, 38, 40,42, IM application 44 and IM database 46 shown in FIG. 1. The mobilecommunication device 400 includes a processing subsystem 438, acommunications subsystem 411, a short-range communications subsystem440, a memory subsystem 424, 426, and various other device subsystemsand/or software modules 442. The mobile communication device 400 alsoincludes a user interface, which may include a display 422, a keyboard430, a speaker 432, a microphone 436, one or more auxiliary input/outputdevices 428, a serial port 430, and/or other user interface devices.

The processing subsystem 438 controls the overall operation of themobile communication device 400. Operating system software executed bythe processing subsystem 438 may be stored in a persistent store, suchas a flash memory 424, but may also be stored in other types of memorydevices in the memory subsystem, such as a read only memory (ROM) orsimilar storage element. In addition, system software, specific deviceapplications, or parts thereof, may be temporarily loaded into avolatile store, such as a random access memory (RAM) 426. Communicationsignals received by the mobile communication device 400 may also bestored to RAM 426.

The processing subsystem 438, in addition to its operating systemfunctions, enables execution of software applications 424 on the device400. A predetermined set of applications that control basic deviceoperations, such as data and voice communications, may be installed onthe device 400 during manufacture. For example, a personal informationmanager (PIM) application, including an electronic messagingapplication, may be installed on the device. The PIM may, for example,be operable to organize and manage data items, such as email, calendarevents, voice mails, appointments, and task items. The PIM applicationmay also be operable to send and receive data items via the wirelessnetwork 419. Another application that may be installed on the device isthe instant messaging application 44 shown in FIG. 1. These applicationsoperated in conjunction with data stored in the Flash memory 424 or RAM426. For example, the instant messaging configuration data files 36, 38,40, 42, instant messaging database 46, and community-specific icon code28, 30, 32, 34 may be stored in the Flash memory 424.

Communication functions, including data and voice communications, areperformed through the communication subsystem 411, and possibly throughthe short-range communications subsystem 440. The communicationsubsystem 411 includes a receiver 412, a transmitter 414 and one or moreantennas 416, 418. In addition, the communication subsystem 411 alsoincludes a processing module, such as a digital signal processor (DSP)420 or other processing device(s), and local oscillators (LOs) 413. Thespecific design and implementation of the communication subsystem 411 isdependent upon the communication network in which the mobilecommunication device 400 is intended to operate. For example, a mobilecommunication device 400 may include a communication subsystem 411designed to operate within the Mobitex™ mobile communication system, theDataTAC™ mobile communication system, a GSM network, a GPRS network, aUMTS network, and/or an EDGE network.

Network access requirements vary depending upon the type ofcommunication system. For example, in the Mobitex and DataTAC networks,mobile communication devices are registered on the network using aunique personal identification number or PIN associated with eachdevice. In UMTS and GSM/GPRS networks, however, network access isassociated with a subscriber or user of a device. A GPRS devicetherefore requires a subscriber identity module, commonly referred to asa SIM card, in order to operate on a GSM/GPRS network.

When required network registration or activation procedures have beencompleted, the mobile communication device 400 may send and receivecommunication signals over the communication network 419. Signalsreceived by the antenna 416 from the communication network 419 arerouted to the receiver 412, which provides signal amplification,frequency down conversion, filtering, channel selection, etc., and mayalso provide analog to digital conversion. Analog-to-digital conversionof the received signal allows the DSP to perform more complexcommunication functions, such as demodulation and decoding. In a similarmanner, signals to be transmitted to the network 419 are processed(e.g., modulated and encoded) by the DSP 420 and are then provided tothe transmitter 414 for digital to analog conversion, frequency upconversion, filtering, amplification and transmission to thecommunication network 419 (or networks) via the antenna 418.

In addition to processing communication signals, the DSP 420 providesfor receiver 412 and transmitter 414 control. For example, gains appliedto communication signals in the receiver 412 and transmitter 414 may beadaptively controlled through automatic gain control algorithmsimplemented in the DSP 420.

In a data communication mode, a received signal, such as a text messageor web page download, is processed by the communication subsystem 411and input to the processing device 438. The received signal is thenfurther processed by the processing device 438 for output to a display422, or alternatively to some other auxiliary I/O device 428. A deviceuser may also compose data items, such as email messages, using akeyboard 438 and/or some other auxiliary I/O device 428, such as atouchpad, a rocker switch, a thumb-wheel, or some other type of inputdevice. The composed data items may then be transmitted over thecommunication network 419 via the communication subsystem 411.

In a voice communication mode, overall operation of the device issubstantially similar to the data communication mode, except thatreceived signals are output to a speaker 434, and signals fortransmission are generated by a microphone 436. Alternative voice oraudio I/O subsystems, such as a voice message recording subsystem, mayalso be implemented on the device 400. In addition, the display 422 mayalso be utilized in voice communication mode, for example to display theidentity of a calling party, the duration of a voice call, or othervoice call related information.

The short-range communications subsystem 440 enables communicationbetween the mobile communication device 400 and other proximate systemsor devices, which need not necessarily be similar devices. For example,the short-range communications subsystem 440 may include an infrareddevice and associated circuits and components, or a Bluetooth™communication module to provide for communication with similarly-enabledsystems and devices.

The above-described embodiments of the present invention are intended tobe examples only. Those of skill in the art may effect alterations,modifications and variations to the particular embodiments withoutdeparting from the scope of the invention.

1. A mobile instant messaging device for communicating instant messageswith different instant messaging communities, comprising: a display thatdisplays community-specific icons, each icon specifying a different oneof the instant messaging communities; a database that storescharacteristics of each of the communities; and an instant messagingapplication configured to communicate instant messages, with a member ofthe community of any of the icons selected by a user of the device, inconformity with the characteristics stored in the database for thatcommunity.
 2. The instant messaging device of claim 1 wherein thecharacteristics include characteristic appearances for instant messagesfor each respective community.
 3. The instant messaging device of claim1 wherein the characteristics include a lexicon for instant messages foreach respective community.
 4. The instant messaging device of claim 1wherein the characteristics include functionality for each respectivecommunity.
 5. The instant messaging device of claim 1 wherein the iconsare displayed in a one-dimensional array in an interface ribbon.
 6. Theinstant messaging device of claim 1 wherein the icons are displayed in atwo-dimensional array in an interface ribbon.
 7. The instant messagingdevice of claim 1 wherein the database stores the information for eachcommunity in a data file specific for that community.
 8. The instantmessaging device of claim 1 further comprising a wireless interface forcommunicating instant messages to a wireless data network, and akeyboard for entering instant messaging text into the device.
 9. Theinstant messaging device of claim 1 wherein at least one of the icons isconfigured to display community-specific information related to therespective community.
 10. The instant messaging device of claim 9wherein the instant messaging information includes the user's currentpresence information with respect to the respective icon's community.11. The instant messaging device of claim 9 wherein the instantmessaging information includes a number of received messages from therespective icon's community.
 12. The instant messaging device of claim 1wherein the application is configured, in response to detecting atrigger event for one of the communities, to cause the display todisplay the icon for that community.
 13. The instant messaging device ofclaim 12 wherein the trigger event is receiving an invitation to chat,or receiving a service book record that identifies a particular serviceaccessible through the respective community, or entering of a secretcode into the device, or activation of a download file, or clicking on alink in a browser, or receiving an email with a control code foractivating a particular service.
 14. A mobile instant messaging devicefor communicating instant messages with different instant messagingcommunities, comprising: a display that displays community-specificicons, each icon specifying a different one of the instant messagingcommunities, and each icon displaying community-specific informationrelevant to the respective community; and an instant messagingapplication configured to communicate instant messages with a member ofthe community of any one of the icons selected by a user of the device.15. The instant messaging device of claim 14 wherein thecommunity-specific information includes the user's current presenceinformation with respect to the respective community.
 16. The instantmessaging device of claim 14 wherein the community-specific informationincludes a number of received messages from the respective community.17. A mobile instant messaging device for communicating instant messageswith different instant messaging communities, comprising: a display thatdisplays community-specific icons, each icon specifying a different oneof the instant messaging communities; and an instant messagingapplication configured to communicate instant messages, with a member ofthe community of any one of the icons selected by a user of the device,and further configured to cause the display to display the icon for oneof the communities in response to detecting a trigger event related tothat community.
 18. The instant messaging device of claim 17 wherein thetrigger event is receiving an invitation to chat from a member of therespective community.
 19. The instant messaging device of claim 17wherein the trigger event is receiving a service book record thatidentifies a particular service accessible through the respectivecommunity.
 20. The instant messaging device of claim 17 wherein thetrigger event is entering of a secret code into the device, oractivation of a download file, or clicking on a link in a browser, orreceiving an email with a control code for activating a particularservice.